Might want to join forces with #478 ?

I'm not sure about joining with sharerenamer. With all due respect, but I dont like sharerenamer's approach and I would like to keep my app as an alternative to sharerenamer, if that's possible. (Differences can be seen in the screenshots I added to readme recently)
And I'm sorry for the delayed reply.

Hi @jimmyl0l3c
Can you fix this?
https://github.com/nextcloud/app-certificate-requests/pull/484/checks?check_run_id=5188866172

@jimmyl0l3c
Suggestions:
rename your repository from cfg-share-links to cfgsharelinks
OR: rename your repository from cfg-share-links to cfg_share_links and change the app_id to cfg_share_links

Motivation: Make more easy to new developers clone the repository and start to work without necessity to rename the repository folder to same name of app_id

Only a suggestion, waiting for your opinion to go ahead.

Thank you for suggestion and I agree. I will change the app_id and rename repository.
But I need to generate new certificate, am I right?

I think that will be not necessary generate but, isn't a problem to generate a new certificate, rename the folder and certificate name to maintain equals to app_id. This isn't a problem to do this for now because we don't merged your certificate to app certificate repository.

But "Subject" field in certificate request would be wrong if I didnt generate new one. Isn't it a problem?

Certificate Request:
    Data:
        Version: 1 (0x0)
        Subject: CN = cfgsharelinks
...

EDIT: Also I may have misunderstood the beginning of your post. I will push new certificate in a minute.

App_id is changed, repo renamed and I committed new certificate.

Beautiful! Can you squash all into only one commit?

crt here: d2a4ca6

Thank you